home *** CD-ROM | disk | FTP | other *** search
- IMPORTANT RELEASE NOTES FOR FITTER V2.1 : 8/5/1995
- =======================================
-
- A host of new additions, changes and fixes have been made for Fitter
- V2.1. Note that this archive contains Fitter V2.11 a maintenance
- release for V2.1. To see what's been fixed, look at the HISTORY
- section of the documentation
-
- Please note the following:
-
- ------------------------------------------------------------------------
-
- Amigaguide help on WB2.X machines has only been found to work when
- using Amigaguide V34.X. During the author's own tests (on a WB2.1
- A500), running with amigaguide.library V39.x immediately crashes.
- It's probably a simple procedure to code around this crash (if I know
- exactly the way to check if I'm on a pre-WB3.X machine), but I haven't
- invested the time in this. For WB2.x machines, amigaguide.library
- V34.X seems to work fine. I obtained this from Aminet, in the
- AmigaGuide development package.
-
- ------------------------------------------------------------------------
-
- With the addition of the new disk labeling feature, it's important to
- note that Fitter maintains the names of each disk label in a Fitter
- catalog, but Fitter still internally has a disk number for each disk.
- It's therefore easier to maintain your disks physically by writing
- their disk #s on them so that the'yre easier to locate when Fitter
- asks you for them.
-
- ------------------------------------------------------------------------
-
- Although Fitter V2.0 was designed to be backwardly compatible with
- Fitter V1.X, a bug existed which caused older catalogs to be read in,
- with negative amounts of diskspace available for some disks. This has
- been fixed.
-
- Be aware that even if these negative values exist in a catalog you've
- already re-read, it will be fixed when read in by V2.1.
-
- ------------------------------------------------------------------------
-
- The methods Fitter uses to select new and existing disks to use during
- the Add Files procedure has been significantly enhanced for V2.1. For
- those that were concerned about when files are deleted from the source
- directory (using the automatic deleting feature), the deletions now
- happen *by the disk*, as opposed to *by the file*. In other words,
- files are deleted from the source directory after the Add Files is
- finished using the disk it's on.
-
- ------------------------------------------------------------------------
-
- Please see the History section of the docs for complete release info;
- all new features and bug fixes.
-
- Please send any inquiries by email to: benjamin@ritz.mordor.com
-